- Retrieve and track the GitHub repository ID during creation or check
- Generate Netlify deploy keys and register public keys to the synced GitHub repository
- Supply `repo_id` and `deploy_key_id` to Netlify site creation, update, and build API requests
- Add test coverage and mock endpoints in `deploy.test.ts`

Addresses multiple edge cases, potential race conditions, and synchronization
performance across Vercel, Railway, Render, Netlify, and GitHub deployment paths:

- Vercel: Automatically resolves `teamId` from `teamSlug` via `GET /v2/teams`
  to correctly scope deployment status queries.
- Railway: Adds an `isNewService` check on service creation to skip duplicate
  manual trigger builds. Propagates unified `DeployError` on V1+V2 mutation failures.
- Render: Introduces a robust polling mechanism (`pollRenderDeploy`) using
  `GET /services/{serviceId}/deploys/{deployId}` to catch and propagate build failures.
- Netlify: Avoids socket hangups on trigger builds using a 15-second abort signal
  timeout. Restricts `/deploys` fallback query to successful trigger builds, and
  carries repo visibility (`isPrivate`) into the link settings.
- GitHub: Extracts and unifies repository verification/creation into a common
  `ensureGitHubRepository` helper which handles 422 concurrent creation race conditions.
- Git Blob SHA Optimization: Implements local Git Blob SHA calculation (`gitBlobSha`)
  and updates `createOrUpdateGitHubFile` to query remote file SHAs, skipping the
  PUT request if the file content matches.

Added/updated regression tests in deploy.test.ts to verify the new behaviors.

…ty conflicts

This fixes two critical deploy flow issues:

1. Netlify deploy key accumulation:
- Netlify site deploy_key_id is now persisted under providerMetadata.
- On redeployment, the existing key is retrieved from priorMetadata, or fetched from the Netlify site object (checking deploy_key_id, repo.deploy_key_id, and build_settings.deploy_key_id).
- A new deploy key is only created if none was resolved.
- Added a regression test verifying keys are not generated on subsequent runs.

2. Cross-provider repo visibility conflicts:
- Namespaced GitHub repositories to be provider-specific ('od-netlify-\', 'od-render-\', and 'od-railway-\').
- This ensures Render and Railway can safely clone their public repositories, even if Netlify has configured its own repository as private.
- Updated all test mock configurations to match the new namespaces.

…y and Render

This addresses an edge case where a user's default branch on GitHub is not 'main' (e.g. 'master'):

1. Updated ensureGitHubRepository to return the defaultBranch extracted from the GitHub API response, falling back to 'main' if not found.
2. Replaced the hard-coded 'main' branch string in deployToNetlify (creation and update payloads) with defaultBranch.
3. Replaced the hard-coded 'main' branch string in deployToRender (service creation payload) with defaultBranch.
4. Added unit tests for Netlify and Render validating correct propagation of non-main branches (e.g., 'master').

…back

This addresses a race condition in the Netlify build trigger fallback:

1. Query and store the latest deploy ID from Netlify before calling POST /sites/{id}/builds.
2. In the fallback path (when the trigger succeeds but omits the deploy_id), poll the deploys list up to 5 times (1s intervals).
3. Verify that the resolved deploy ID differs from the pre-trigger deploy ID to ensure we don't bind to a stale previous run, throwing a DeployError if none is resolved.
4. Suppressed mock-related fetch logs in Vitest run environments.
5. Added a regression test: 'polls and resolves new Netlify deploy when trigger response lacks deploy_id and new deploy is delayed'.

…ain resolution

… test mocks

This addresses a social share retry provider mismatch and localizes the daemon test fetch mock wrapper to prevent global Vitest worker pollution.

Thread target provider ID (via latestSocialShareDeployment?.providerId) into retryDeploymentLink inside FileViewer.tsx.

In retryDeploymentLink, search for active deployment targeting the specified provider ID, falling back to the current modal-level deployProviderId.

Removed the top-level global monkeypatch of vi.stubGlobal from deploy.test.ts to keep Vitest environment clean.

Added a local stubGlobalFetch(fetchMock) helper inside deploy.test.ts to wrap fetch mocks and handle unexpected git/trees/ calls locally.

Updated all fetch mocking tests in deploy.test.ts to use stubGlobalFetch instead of vi.stubGlobal('fetch').

This addresses a race condition and error mapping in the Railway and GitHub deploy processes:
- Query and store the latest deploy ID from Railway before triggering build.
- Poll the deploys list up to 5 times (1s intervals) to resolve the new deploy ID, verifying it differs from the pre-trigger deploy ID.
- Poll the resolved Railway deployment until status becomes ACTIVE.
- Support specific Railway deployment status queries in check-link endpoint.
- Map GitHub upload/PUT failures to 502 Bad Gateway.
- Verify that social share auto-opening transition is only executed if the deploy modal was opened from the share flow.

…elays

This addresses a correctness issue where Render deploy IDs are missing or delayed:
- Fetch and record latest deploy ID before triggering build as preTriggerDeployId.
- Poll Render deploys list up to 5 times (1s intervals) to resolve the new deploy ID, verifying it differs from preTriggerDeployId.
- Persist resolved deploy ID in providerMetadata.
- Add regression test: 'polls and resolves new Render deploy when trigger response lacks deploy_id and new deploy fails'.

…cess in check-link

This addresses correctness and reliability in PaaS deployment flows:

Query Netlify using GET /deploy_keys/:id to fetch the public key during deploy key reuse, ensuring it is repaired/registered on GitHub, or rotating the key pair if missing.

Add provider-specific check-link handlers checkNetlifyDeploymentLinks and checkRenderDeploymentLinks that query the deployment/build status from the Netlify and Render APIs, falling back to reachability checks once confirmed ready.

Wire Netlify and Render check-link handlers into the daemon check-link route and server dependencies.

Added unit tests to verify checkNetlifyDeploymentLinks and checkRenderDeploymentLinks behavior across ready, building, and failed states, and updated Netlify key reuse test to assert GitHub registration.

… button in FileViewer

… deploy key

Add validation queries at the start of Netlify, Render, and Railway deploys. Stored site, service, and project IDs are treated as hints and cleared if the provider returns a 404 / Not Found error, triggering name-based re-resolution and recreation.

Whitelist 422 validation duplicate key errors from GitHub (e.g. "key is already in use") during deploy key registration to allow healthy redeploys to succeed.

Add unit tests covering recovery from stale resource IDs and handling of duplicate GitHub deploy keys.

…ne deploy ID verification

Throw a DeployError on non-OK responses from Netlify and Render site/service list queries to prevent duplicate site/service creation during transient API errors.

Enforce baseline pre-trigger deployment ID verification in Netlify and Render. If the pre-trigger deploy check fails, leave the baseline ID as undefined and throw a DeployError if the trigger response omits the build/deploy ID, preventing the fallback from accepting a stale deployment.

Add unit tests covering list lookup errors and pre-trigger check failures.

…ues and query timeout budget

…on and web

- Resolved merge conflicts in apps/web/src/components/FileViewer.tsx by correctly shifting deploy actions and copy links from the download dropdown to the share/publish dropdown.
- Configured individual provider copy links to only show when there are multiple active deployments (threshold > 1) to eliminate single-item redundancy.
- Fixed a bug in deployToRailway where a DeployError was incorrectly thrown even if the fallback mutation succeeded.
- Fixed a mock pollution issue in deploy.test.ts GET requests by restricting getHeaders capture to target files.
- Added missing PUT config mock and asynchronous state wait race condition handling in FileViewer.test.tsx.

…style tests

… segments

…ght worker fixture ownership

…s test